Subject: NM Requirements for Extended Border Node

From: "Katie Lee" <[email-masked]>
Date: Tue, 27 Aug 96 13:36:12 EDT

The following are the EBN network management requirements that
we were addressing with the proposed EBN mib presented at
AIW 11.  Comments and additional requirements are requested.

1.Determine which LU names are in the native subnetwork and which
are in a non-native subnetwork.  Currently in the APPN MIB, the
contents of the Directory database available to a NM station.  For
an EBN, it is useful to indicate whether an LU is in the native
subnetwork or a non-native subnetwork.
(This is the requirement for the proprosed extension of the
appnEbnDirTable.)

2.Diagnose route/session establishment failures due to:
    COS-based reasons
    (This is the requirement for the proposed Cos Mapping Group.)
    Search failures
      - incomplete or incorrect subnet routing list
      - inadequate SNVC
      (This is the requirement for the proposed Border Node Search List
       group.)

3.Enable the network manager to retrieve and inspect all RSCVs pertaining
to an active session traversing EBNs, in case a session problem is
reported.  Since EBNs replace the incoming BIND RSCV with a cached
RSCV, it is necessary to enable collection of RSCVs at each EBN.
(This is the requirement for the proposed extension to the ISR table,
as discussed at the AIW MIB SIG.)

Regards,
Katie Lee